Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: multi regional deployment pipeline #218

Closed
wants to merge 2 commits into from
Closed

Conversation

eedygreen
Copy link
Collaborator

Description

Deploy Relayers to other regions with an option to choose which region to deploy. Simply enter the AWS region name to deploy to that region.

Related Issue Or Context

Multi region deployment

Related #193

@eedygreen eedygreen changed the title chore: regional deployment pipeline chore: multi regional deployment pipeline Sep 22, 2023
@github-actions
Copy link
Contributor

Go Test coverage is 65.7 %\ ✨ ✨ ✨

name: sygma_deploy_devnet_to_regions

on:
workflow_dispatch:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should not it be on push, the same it was before?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

workflow dispatch does not need push commit. If we are going to deploy manually, then the commit is not manual.

@@ -54,7 +54,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
relayer_id: [0, 1, 2, 3, 4]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not like that we are basically having copy of this file just to deploy to another region. Might we use if statements with matrix values? like if matrix.relayer_id.3 deploy to this region, etc.
Or for example we can use include statement of GA that allwos to add additional arguments to particular matrix elements. And we can use it to specify region per relayer_id

@eedygreen eedygreen closed this Sep 28, 2023
@eedygreen eedygreen deleted the mumbai_pipeline branch September 28, 2023 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants